Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: dac76f5d2cf705f094e0c4e9c23ebafbd71792893171589eef3046b0e5abc3c4

Tx prefix hash: 8ddb41bde38020eae1c21449d03bc71a242eb5625642c7e4408cdcde7a6ce2f1
Tx public key: 79860d1e9d5f28b2197b7a1729db703f62351b094013bb5c01d8e104d076b9b9
Timestamp: 1724437462 Timestamp [UCT]: 2024-08-23 18:24:22 Age [y:d:h:m:s]: 00:232:06:45:26
Block: 1094360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165857 RingCT/type: yes/0
Extra: 0179860d1e9d5f28b2197b7a1729db703f62351b094013bb5c01d8e104d076b9b902110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78e9e7ce4b5611c9ebb2de532e56f0ba79e4d33cbc9b6049d57f99647a70d6e7 0.600000000000 1569477 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1094370, "vin": [ { "gen": { "height": 1094360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78e9e7ce4b5611c9ebb2de532e56f0ba79e4d33cbc9b6049d57f99647a70d6e7" } } ], "extra": [ 1, 121, 134, 13, 30, 157, 95, 40, 178, 25, 123, 122, 23, 41, 219, 112, 63, 98, 53, 27, 9, 64, 19, 187, 92, 1, 216, 225, 4, 208, 118, 185, 185, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8