Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7b4a4e11fdb9b342946fd5994ab1ae7890273606e21a5d440e9b5c1b3a1f9fc

Tx prefix hash: 3eb0272637bc241d719a90ebfd7861f4f5037ddf753778cfd69b5916141af37f
Tx public key: bc551a74b7e57db9aa2896f2670bc2417566e781e88db752d1cfe272e822b966
Timestamp: 1731096444 Timestamp [UCT]: 2024-11-08 20:07:24 Age [y:d:h:m:s]: 00:132:09:58:37
Block: 1149471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94462 RingCT/type: yes/0
Extra: 01bc551a74b7e57db9aa2896f2670bc2417566e781e88db752d1cfe272e822b966021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7afd18c0650926f6b16d6a1f85cf64526923ae36562e20a7d8a62ca2224f985 0.600000000000 1634556 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": 1149481, "vin": [ { "gen": { "height": 1149471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7afd18c0650926f6b16d6a1f85cf64526923ae36562e20a7d8a62ca2224f985" } } ], "extra": [ 1, 188, 85, 26, 116, 183, 229, 125, 185, 170, 40, 150, 242, 103, 11, 194, 65, 117, 102, 231, 129, 232, 141, 183, 82, 209, 207, 226, 114, 232, 34, 185, 102, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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