Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24f8c3e40385f45ce96cb172591d7e39ce5eade56acbe51934a703d0802ac058

Tx prefix hash: 8d9e5bdd64fdbcaf65517c641d1cf24ad273b93c237390a12f755a7ffdc5ce8f
Tx public key: 6946bfca7bfb37d66d7881752a37b70767ac6f4c8eec1ae4f8f67dccd5100b38
Timestamp: 1724204883 Timestamp [UCT]: 2024-08-21 01:48:03 Age [y:d:h:m:s]: 00:254:04:03:55
Block: 1092424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181530 RingCT/type: yes/0
Extra: 016946bfca7bfb37d66d7881752a37b70767ac6f4c8eec1ae4f8f67dccd5100b38021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8277743712a66ac619eef175f09066eee0aebaa0ac230f71036715f1d7f0bc76 0.600000000000 1567167 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": 1092434, "vin": [ { "gen": { "height": 1092424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8277743712a66ac619eef175f09066eee0aebaa0ac230f71036715f1d7f0bc76" } } ], "extra": [ 1, 105, 70, 191, 202, 123, 251, 55, 214, 109, 120, 129, 117, 42, 55, 183, 7, 103, 172, 111, 76, 142, 236, 26, 228, 248, 246, 125, 204, 213, 16, 11, 56, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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