Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b59a5e2021906bf74a772009d9176994c1991fbfebec2dfc5e2bf85385303a2

Tx prefix hash: 83380c3c270032446b5eab8b3043516f36b1216e722ac8b44246e56d91a76d6f
Tx public key: b309ca272ea7c4ae0d92b9fddb4d843849cadc8ca7007cd4f1340b24a6352e47
Timestamp: 1664507019 Timestamp [UCT]: 2022-09-30 03:03:39 Age [y:d:h:m:s]: 02:209:13:33:50
Block: 598624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 671368 RingCT/type: yes/0
Extra: 01b309ca272ea7c4ae0d92b9fddb4d843849cadc8ca7007cd4f1340b24a6352e4702110000000275e3f0e9000000000000000000

1 output(s) for total of 6.375441266000 dcy

stealth address amount amount idx
00: e0c2f9d9f6eba08673ebeb9b73e04429d4a4fb0e2ed0ea93e9c4c0dac2ea806e 6.375441266000 1034409 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": 598634, "vin": [ { "gen": { "height": 598624 } } ], "vout": [ { "amount": 6375441266, "target": { "key": "e0c2f9d9f6eba08673ebeb9b73e04429d4a4fb0e2ed0ea93e9c4c0dac2ea806e" } } ], "extra": [ 1, 179, 9, 202, 39, 46, 167, 196, 174, 13, 146, 185, 253, 219, 77, 132, 56, 73, 202, 220, 140, 167, 0, 124, 212, 241, 52, 11, 36, 166, 53, 46, 71, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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