Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4559c4a5b7fec6fc8b78e9d623e8dfb06d9fe6012a091f0d7240966220f4ab78

Tx prefix hash: c029c2b5ec5d65e91deb5e9c4803096c337759597a5223a22cbd1814386ab517
Tx public key: a2b7d315debfe9e24f313dd7a0d091a8f4e0399d47f138183445e9bce87e859d
Timestamp: 1582508705 Timestamp [UCT]: 2020-02-24 01:45:05 Age [y:d:h:m:s]: 05:251:11:57:54
Block: 71117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1330846 RingCT/type: yes/0
Extra: 01a2b7d315debfe9e24f313dd7a0d091a8f4e0399d47f138183445e9bce87e859d021100000001724f989b000000000000000000

1 output(s) for total of 356.747270493000 dcy

stealth address amount amount idx
00: 7b9b4a7ad1516310161c9f588acfc4a98baeba9d9a2178d5a9af6508c66f88db 356.747270493000 131436 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": 71127, "vin": [ { "gen": { "height": 71117 } } ], "vout": [ { "amount": 356747270493, "target": { "key": "7b9b4a7ad1516310161c9f588acfc4a98baeba9d9a2178d5a9af6508c66f88db" } } ], "extra": [ 1, 162, 183, 211, 21, 222, 191, 233, 226, 79, 49, 61, 215, 160, 208, 145, 168, 244, 224, 57, 157, 71, 241, 56, 24, 52, 69, 233, 188, 232, 126, 133, 157, 2, 17, 0, 0, 0, 1, 114, 79, 152, 155, 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