Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d56f78a4e11a99bd45168f61dd9591098f7ff74560c0528a8d412af307a0f78

Tx prefix hash: 1c51413e41d5b9c801225c16ca752ab6fed5d1e5d86d37a58148206faab421aa
Tx public key: 0c9a21d9e4b423354dc578924b492bd1c82c2358ab1f3e258877fa808afca8dc
Timestamp: 1632443401 Timestamp [UCT]: 2021-09-24 00:30:01 Age [y:d:h:m:s]: 03:043:20:45:33
Block: 339756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 807578 RingCT/type: yes/0
Extra: 010c9a21d9e4b423354dc578924b492bd1c82c2358ab1f3e258877fa808afca8dc021100000010f29d7abf000000000000000000

1 output(s) for total of 45.946006012000 dcy

stealth address amount amount idx
00: 18cdc64de6c6d31af3e5ffc1f7cd42afde7a1f3d49a56f69724baedf5e2dd379 45.946006012000 698641 of 0

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": 339766, "vin": [ { "gen": { "height": 339756 } } ], "vout": [ { "amount": 45946006012, "target": { "key": "18cdc64de6c6d31af3e5ffc1f7cd42afde7a1f3d49a56f69724baedf5e2dd379" } } ], "extra": [ 1, 12, 154, 33, 217, 228, 180, 35, 53, 77, 197, 120, 146, 75, 73, 43, 209, 200, 44, 35, 88, 171, 31, 62, 37, 136, 119, 250, 128, 138, 252, 168, 220, 2, 17, 0, 0, 0, 16, 242, 157, 122, 191, 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