Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7911a847f1f24f744b5491b824f655ae23dfc216e6ad9310d78464bd476ed252

Tx prefix hash: 977d1a32ba1ea30b1eebd06daa6369d8686c42aa02712966bb406acf6e4d4d57
Tx public key: 8f2c884636bf57b79695ed66fe6aa9e49d0134f91d5ae8ab06ccbc48dbc3bb7c
Timestamp: 1707793227 Timestamp [UCT]: 2024-02-13 03:00:27 Age [y:d:h:m:s]: 01:058:00:30:14
Block: 956344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302523 RingCT/type: yes/0
Extra: 018f2c884636bf57b79695ed66fe6aa9e49d0134f91d5ae8ab06ccbc48dbc3bb7c0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c6b384e517bde000cc4a993efc45306bc011ad6a350a9f41998f8d994d1d001 0.600000000000 1415648 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": 956354, "vin": [ { "gen": { "height": 956344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c6b384e517bde000cc4a993efc45306bc011ad6a350a9f41998f8d994d1d001" } } ], "extra": [ 1, 143, 44, 136, 70, 54, 191, 87, 183, 150, 149, 237, 102, 254, 106, 169, 228, 157, 1, 52, 249, 29, 90, 232, 171, 6, 204, 188, 72, 219, 195, 187, 124, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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