Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 882e45d6e70aa98646914ece196a46491ec84a0509ccedd7710e9fb0c07c86fa

Tx prefix hash: 3375fb80db029b2161409aa80c7021f0df352c75ce96f72d5baa17a188bc9df4
Tx public key: 40a0d924a39e4b535f52a478112e45ed9fe9a727565aee13c54a70525ece585e
Timestamp: 1713246598 Timestamp [UCT]: 2024-04-16 05:49:58 Age [y:d:h:m:s]: 01:028:12:08:12
Block: 1001547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281368 RingCT/type: yes/0
Extra: 0140a0d924a39e4b535f52a478112e45ed9fe9a727565aee13c54a70525ece585e021100000002679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85137fcc8ac1c7fbe95c6d01361def816fb46d602c9ff49083073b57ae1123ae 0.600000000000 1462053 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": 1001557, "vin": [ { "gen": { "height": 1001547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85137fcc8ac1c7fbe95c6d01361def816fb46d602c9ff49083073b57ae1123ae" } } ], "extra": [ 1, 64, 160, 217, 36, 163, 158, 75, 83, 95, 82, 164, 120, 17, 46, 69, 237, 159, 233, 167, 39, 86, 90, 238, 19, 197, 74, 112, 82, 94, 206, 88, 94, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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