Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e57aee055d77ce8c600f368b01f4b07b939ab5ed1fd684807e912c92484dfd06

Tx prefix hash: 1921a102b23b96b627ebdcd8e119f16a7a0fdb3090d5061b2d4c627518a31e0a
Tx public key: 5d9eb0a43cc4980120b24a865f57e32e1232a1d508d1272ef39634973104f085
Timestamp: 1710447914 Timestamp [UCT]: 2024-03-14 20:25:14 Age [y:d:h:m:s]: 01:294:11:27:44
Block: 978380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469235 RingCT/type: yes/0
Extra: 015d9eb0a43cc4980120b24a865f57e32e1232a1d508d1272ef39634973104f0850211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6b9d0e7b1b1dcc2a41a10025614a604c3897ca3fb2d544d42f748717be6cbf6 0.600000000000 1438405 of 15

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": 978390, "vin": [ { "gen": { "height": 978380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6b9d0e7b1b1dcc2a41a10025614a604c3897ca3fb2d544d42f748717be6cbf6" } } ], "extra": [ 1, 93, 158, 176, 164, 60, 196, 152, 1, 32, 178, 74, 134, 95, 87, 227, 46, 18, 50, 161, 213, 8, 209, 39, 46, 243, 150, 52, 151, 49, 4, 240, 133, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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