Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6eeb284d9789a9c87036f6210785682909a15c06778a0ca2388e548c32c4215c

Tx prefix hash: 5218f13ffd6abae71ae10867f958c33b29a13875bdf1323aecbe2d571829e396
Tx public key: 613a9b1ef5731632846c6fe13efe8cdb5c67853d47263b038a5f1176e01e946c
Timestamp: 1722244287 Timestamp [UCT]: 2024-07-29 09:11:27 Age [y:d:h:m:s]: 00:238:00:36:56
Block: 1076166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170008 RingCT/type: yes/0
Extra: 01613a9b1ef5731632846c6fe13efe8cdb5c67853d47263b038a5f1176e01e946c021100000001b6cd74da000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7eae5afd775fcc6b4b3034f476e761577fdc827196c3fd1476c7a57d6f4424e5 0.600000000000 1548701 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": 1076176, "vin": [ { "gen": { "height": 1076166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7eae5afd775fcc6b4b3034f476e761577fdc827196c3fd1476c7a57d6f4424e5" } } ], "extra": [ 1, 97, 58, 155, 30, 245, 115, 22, 50, 132, 108, 111, 225, 62, 254, 140, 219, 92, 103, 133, 61, 71, 38, 59, 3, 138, 95, 17, 118, 224, 30, 148, 108, 2, 17, 0, 0, 0, 1, 182, 205, 116, 218, 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