Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f7b31ad9b8be176ffdf5d45fc750523c1995857e9fe955554dc0964a139ab4d

Tx prefix hash: 0e51f0b4b29366c1638850782aca3104e211aa56ebd6b63fb684ccbe7e848596
Tx public key: c6aa89c0b396a8f905c463242ea6ed2a6fa89debb4e761757c03414937364d87
Timestamp: 1738625699 Timestamp [UCT]: 2025-02-03 23:34:59 Age [y:d:h:m:s]: 00:289:08:26:30
Block: 1211534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204571 RingCT/type: yes/0
Extra: 01c6aa89c0b396a8f905c463242ea6ed2a6fa89debb4e761757c03414937364d87021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5083dae2cc61bfb163d66c8be4d850bb916773977effc5d2f413c385976e0283 0.600000000000 1698295 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": 1211544, "vin": [ { "gen": { "height": 1211534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5083dae2cc61bfb163d66c8be4d850bb916773977effc5d2f413c385976e0283" } } ], "extra": [ 1, 198, 170, 137, 192, 179, 150, 168, 249, 5, 196, 99, 36, 46, 166, 237, 42, 111, 168, 157, 235, 180, 231, 97, 117, 124, 3, 65, 73, 55, 54, 77, 135, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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