Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebf4ef513612f8660d4f72b0f6947cb5fc6df118ce743e1ecba044cdfdd2f8bf

Tx prefix hash: fdd41dea20757fdec05011359161d68b65730faff0e5ab5d41b8e8240528b6de
Tx public key: 17287e5063a5478b3be214b17de963df6ca5359c1be5079973d019cdacb15258
Timestamp: 1658022963 Timestamp [UCT]: 2022-07-17 01:56:03 Age [y:d:h:m:s]: 02:174:13:04:27
Block: 545401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 646136 RingCT/type: yes/0
Extra: 0117287e5063a5478b3be214b17de963df6ca5359c1be5079973d019cdacb15258021100000001cb8520c2000000000000000000

1 output(s) for total of 9.568860413000 dcy

stealth address amount amount idx
00: 821aea07e202c9f8aedcf03a8c79a0f8880deb96f1308f11fea68a6d581c5c64 9.568860413000 976290 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": 545411, "vin": [ { "gen": { "height": 545401 } } ], "vout": [ { "amount": 9568860413, "target": { "key": "821aea07e202c9f8aedcf03a8c79a0f8880deb96f1308f11fea68a6d581c5c64" } } ], "extra": [ 1, 23, 40, 126, 80, 99, 165, 71, 139, 59, 226, 20, 177, 125, 233, 99, 223, 108, 165, 53, 156, 27, 229, 7, 153, 115, 208, 25, 205, 172, 177, 82, 88, 2, 17, 0, 0, 0, 1, 203, 133, 32, 194, 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