Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47e1ebe3d1ad80d68fffe11363b1550f10c5b74f6af45949198b03b9d640b472

Tx prefix hash: 79aa918814afb851a6f910ea6a81ba81f453a78fb49cddca79a57f9250b606d9
Tx public key: 83e5e6f9916e50c3ca63c4a9b20e60c40e0b0f7ac51872107369839c8b492d13
Timestamp: 1720871354 Timestamp [UCT]: 2024-07-13 11:49:14 Age [y:d:h:m:s]: 01:117:07:21:25
Block: 1064789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342343 RingCT/type: yes/0
Extra: 0183e5e6f9916e50c3ca63c4a9b20e60c40e0b0f7ac51872107369839c8b492d1302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4855177a83919dad87a66b0f4905ebf34aeca1689f22811c1c235a34c5d22350 0.600000000000 1535328 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": 1064799, "vin": [ { "gen": { "height": 1064789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4855177a83919dad87a66b0f4905ebf34aeca1689f22811c1c235a34c5d22350" } } ], "extra": [ 1, 131, 229, 230, 249, 145, 110, 80, 195, 202, 99, 196, 169, 178, 14, 96, 196, 14, 11, 15, 122, 197, 24, 114, 16, 115, 105, 131, 156, 139, 73, 45, 19, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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