Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d125bbc72310e226fb0f6ba51c40d612354b7b7a9aa57b4a8c75d16bfc90be2c

Tx prefix hash: 4a8c5afe44b97112358d32544d5a0d8d446611f02acbff0b8b942009a7e50623
Tx public key: e831f31d53432f675a8ce27457bc19d81d1575d52e6cb59db2b0b499fd3e7790
Timestamp: 1706633216 Timestamp [UCT]: 2024-01-30 16:46:56 Age [y:d:h:m:s]: 01:281:08:56:33
Block: 946717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459885 RingCT/type: yes/0
Extra: 01e831f31d53432f675a8ce27457bc19d81d1575d52e6cb59db2b0b499fd3e779002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59a71fdc74835acecb9d8be28dcfa2c194406bef85e83a9e792e4bd27a62ca76 0.600000000000 1405057 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": 946727, "vin": [ { "gen": { "height": 946717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59a71fdc74835acecb9d8be28dcfa2c194406bef85e83a9e792e4bd27a62ca76" } } ], "extra": [ 1, 232, 49, 243, 29, 83, 67, 47, 103, 90, 140, 226, 116, 87, 188, 25, 216, 29, 21, 117, 213, 46, 108, 181, 157, 178, 176, 180, 153, 253, 62, 119, 144, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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