Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae5210d955ef37db6044f7f47c79b465b60c9a4fc95a820891533ec99eb2c54e

Tx prefix hash: d8e7e9775a38a8f80083ced9c7210a8417e42d6bd9ed89b1429a9a24b74b7205
Tx public key: 4c095f81cdc0aed93bd8f146f316bc311d4c437c86f0f76bb6acd2e80c98856e
Timestamp: 1574549100 Timestamp [UCT]: 2019-11-23 22:45:00 Age [y:d:h:m:s]: 05:102:10:02:03
Block: 15973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1215872 RingCT/type: yes/0
Extra: 014c095f81cdc0aed93bd8f146f316bc311d4c437c86f0f76bb6acd2e80c98856e021100000009f95225a5000000000000000000

1 output(s) for total of 543.425945151000 dcy

stealth address amount amount idx
00: 7472155f815cb935a1bc0d9a5dbf0a17b2493c5e83a7e9e61c4c35ad6d047f87 543.425945151000 21913 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": 15983, "vin": [ { "gen": { "height": 15973 } } ], "vout": [ { "amount": 543425945151, "target": { "key": "7472155f815cb935a1bc0d9a5dbf0a17b2493c5e83a7e9e61c4c35ad6d047f87" } } ], "extra": [ 1, 76, 9, 95, 129, 205, 192, 174, 217, 59, 216, 241, 70, 243, 22, 188, 49, 29, 76, 67, 124, 134, 240, 247, 107, 182, 172, 210, 232, 12, 152, 133, 110, 2, 17, 0, 0, 0, 9, 249, 82, 37, 165, 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