Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57c603c351c0afc1d87361a5306939a15cfd2eb5b6969720138c33fd3b1990a2

Tx prefix hash: 37d2e7b9b30340e6d472d671ff40c707000a03294c2b8f6afbaf09209c1bdd3a
Tx public key: 9845e48d8adca0b2051993bcee0f6ff60b460ec95fdce46acc28aff6510cf84d
Timestamp: 1648908905 Timestamp [UCT]: 2022-04-02 14:15:05 Age [y:d:h:m:s]: 02:317:23:25:22
Block: 471688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 746714 RingCT/type: yes/0
Extra: 019845e48d8adca0b2051993bcee0f6ff60b460ec95fdce46acc28aff6510cf84d0211000000102e6b1fd5000000000000000000

1 output(s) for total of 16.791987257000 dcy

stealth address amount amount idx
00: 34d25502eb07925c4dbef036a94bf192ec4f8b7a183baff8ea70bc5e0e904f96 16.791987257000 891072 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": 471698, "vin": [ { "gen": { "height": 471688 } } ], "vout": [ { "amount": 16791987257, "target": { "key": "34d25502eb07925c4dbef036a94bf192ec4f8b7a183baff8ea70bc5e0e904f96" } } ], "extra": [ 1, 152, 69, 228, 141, 138, 220, 160, 178, 5, 25, 147, 188, 238, 15, 111, 246, 11, 70, 14, 201, 95, 220, 228, 106, 204, 40, 175, 246, 81, 12, 248, 77, 2, 17, 0, 0, 0, 16, 46, 107, 31, 213, 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