Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 537574cb87fd659e9d1e4911512d0387a10e0d85f0047056d3a46b496914ec8c

Tx prefix hash: 747061a49da6a126844ac0369758c399bebde576bfbdc5bf20431905e4945bff
Tx public key: c108dc47ee7d0dec77964fa0052c752affed902e4a73f1a9e74ebfbbbe2d1120
Timestamp: 1578164851 Timestamp [UCT]: 2020-01-04 19:07:31 Age [y:d:h:m:s]: 04:330:07:39:59
Block: 38742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1125233 RingCT/type: yes/0
Extra: 01c108dc47ee7d0dec77964fa0052c752affed902e4a73f1a9e74ebfbbbe2d1120021100000066391a8d0e000000000000000000

1 output(s) for total of 456.701587169000 dcy

stealth address amount amount idx
00: 3dd4050d30fd5ffa2b572f97472fa2aa2f81db3c7aa05f44a863378ba6aec4c7 456.701587169000 66268 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": 38752, "vin": [ { "gen": { "height": 38742 } } ], "vout": [ { "amount": 456701587169, "target": { "key": "3dd4050d30fd5ffa2b572f97472fa2aa2f81db3c7aa05f44a863378ba6aec4c7" } } ], "extra": [ 1, 193, 8, 220, 71, 238, 125, 13, 236, 119, 150, 79, 160, 5, 44, 117, 42, 255, 237, 144, 46, 74, 115, 241, 169, 231, 78, 191, 187, 190, 45, 17, 32, 2, 17, 0, 0, 0, 102, 57, 26, 141, 14, 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