Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89e91292302eeee30447d2b9433ccb7f1c66f967261d7cc89469944fa39713dc

Tx prefix hash: 7f84ebc084da8a442faa7f1769909fb07b35210cbfdabb77e2755f2f3e46ca80
Tx public key: a396b1f437ceb7be5b761a48916d2df7237e739199db5de512e552a90d2770f6
Timestamp: 1675493295 Timestamp [UCT]: 2023-02-04 06:48:15 Age [y:d:h:m:s]: 01:332:00:07:07
Block: 689453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498249 RingCT/type: yes/0
Extra: 01a396b1f437ceb7be5b761a48916d2df7237e739199db5de512e552a90d2770f60211000000025029cbac000000000000000000

1 output(s) for total of 3.188276178000 dcy

stealth address amount amount idx
00: a3d4a9a0faff6decb8f90d58a972d851a5a8e32f57fe00a7a17e789907775ba8 3.188276178000 1132129 of 0

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": 689463, "vin": [ { "gen": { "height": 689453 } } ], "vout": [ { "amount": 3188276178, "target": { "key": "a3d4a9a0faff6decb8f90d58a972d851a5a8e32f57fe00a7a17e789907775ba8" } } ], "extra": [ 1, 163, 150, 177, 244, 55, 206, 183, 190, 91, 118, 26, 72, 145, 109, 45, 247, 35, 126, 115, 145, 153, 219, 93, 229, 18, 229, 82, 169, 13, 39, 112, 246, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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