Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49a6f2dd56dbe3914585491aad55308abb9a0c5d244cca3f44277b20ade3e342

Tx prefix hash: 377cdea174c7f27cd55d8a832da07ed2a6346b6b6ae1040748dc1cd7908a695a
Tx public key: 7616a8b3d41d436df78d9c958d57ae2997f9fbc3997a38b8c8cc97716422214c
Timestamp: 1710005047 Timestamp [UCT]: 2024-03-09 17:24:07 Age [y:d:h:m:s]: 01:268:23:45:02
Block: 974701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450990 RingCT/type: yes/0
Extra: 017616a8b3d41d436df78d9c958d57ae2997f9fbc3997a38b8c8cc97716422214c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b2d44c6b63f2c7c38bcd952f9e48fb015330f856a70397d4d29b58fa1eac446 0.600000000000 1434660 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": 974711, "vin": [ { "gen": { "height": 974701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b2d44c6b63f2c7c38bcd952f9e48fb015330f856a70397d4d29b58fa1eac446" } } ], "extra": [ 1, 118, 22, 168, 179, 212, 29, 67, 109, 247, 141, 156, 149, 141, 87, 174, 41, 151, 249, 251, 195, 153, 122, 56, 184, 200, 204, 151, 113, 100, 34, 33, 76, 2, 17, 0, 0, 0, 1, 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