Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44f971bc40bbd62860e601b6b59850edd2d0f131ed8bb52f5ba850eb2f2c4edd

Tx prefix hash: 51eaf958f2551dd5a2f71aabc0b3a72ede9a5aa568941c3fae7cdadc73dbc724
Tx public key: 7afb7c57493750a4d7ab0719e1808eca9bf733cf9425e8f918d0d701fcac32d2
Timestamp: 1717284093 Timestamp [UCT]: 2024-06-01 23:21:33 Age [y:d:h:m:s]: 00:305:20:41:50
Block: 1035049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218576 RingCT/type: yes/0
Extra: 017afb7c57493750a4d7ab0719e1808eca9bf733cf9425e8f918d0d701fcac32d202110000001259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72cee2993cf9e2a032348f130775bb42e2ff922dd015b0ce81b7e5dc561b5ca0 0.600000000000 1503568 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": 1035059, "vin": [ { "gen": { "height": 1035049 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72cee2993cf9e2a032348f130775bb42e2ff922dd015b0ce81b7e5dc561b5ca0" } } ], "extra": [ 1, 122, 251, 124, 87, 73, 55, 80, 164, 215, 171, 7, 25, 225, 128, 142, 202, 155, 247, 51, 207, 148, 37, 232, 249, 24, 208, 215, 1, 252, 172, 50, 210, 2, 17, 0, 0, 0, 18, 89, 218, 211, 245, 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