Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abf507c24c2220e00ef88ceeb38d78fc8f07e8d34dfc87eb0d84b3bc91802c2b

Tx prefix hash: fa6858bfbe423a36ea80626e4b2084d7a3ea2e2048d32aed94724e50c80cd780
Tx public key: d7543a6101a327c90f5407a849380c753e921520d4feee968e79d3db7010403f
Timestamp: 1724385607 Timestamp [UCT]: 2024-08-23 04:00:07 Age [y:d:h:m:s]: 00:225:22:11:30
Block: 1093928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161316 RingCT/type: yes/0
Extra: 01d7543a6101a327c90f5407a849380c753e921520d4feee968e79d3db7010403f021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6b15e16d8575fb4108247235a496dc188ea6648fa6960b5f3a6955ff01c087b 0.600000000000 1568969 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": 1093938, "vin": [ { "gen": { "height": 1093928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6b15e16d8575fb4108247235a496dc188ea6648fa6960b5f3a6955ff01c087b" } } ], "extra": [ 1, 215, 84, 58, 97, 1, 163, 39, 201, 15, 84, 7, 168, 73, 56, 12, 117, 62, 146, 21, 32, 212, 254, 238, 150, 142, 121, 211, 219, 112, 16, 64, 63, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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