Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae8dd881f21abd912c87d3cdfc78c0bd546862a8e71c50537239546576c9aa04

Tx prefix hash: 454cc8582b79345e9033e96ec6f94d441389279092e6e34395eb3edf313c9471
Tx public key: 52cdad7963a437a94849ba77c1271b9a584a09a396e104045fa3b33d35e43cde
Timestamp: 1578131590 Timestamp [UCT]: 2020-01-04 09:53:10 Age [y:d:h:m:s]: 05:129:17:23:40
Block: 38421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1242601 RingCT/type: yes/0
Extra: 0152cdad7963a437a94849ba77c1271b9a584a09a396e104045fa3b33d35e43cde02110000005cff58ae94000000000000000000

1 output(s) for total of 457.821440628000 dcy

stealth address amount amount idx
00: 2d21d5d764d75b766d8b5ed61d015d1d234046489d2e03e22cb09cbb088336b2 457.821440628000 65516 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": 38431, "vin": [ { "gen": { "height": 38421 } } ], "vout": [ { "amount": 457821440628, "target": { "key": "2d21d5d764d75b766d8b5ed61d015d1d234046489d2e03e22cb09cbb088336b2" } } ], "extra": [ 1, 82, 205, 173, 121, 99, 164, 55, 169, 72, 73, 186, 119, 193, 39, 27, 154, 88, 74, 9, 163, 150, 225, 4, 4, 95, 163, 179, 61, 53, 228, 60, 222, 2, 17, 0, 0, 0, 92, 255, 88, 174, 148, 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