Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cfcdfb0e377e8eb966152e81e9b4329cef7e794c8190eabdb3ee7860b2be7e1

Tx prefix hash: 019eedc6a2535189629c4242ad09618ea86e470aad401cbdd5464640c62d360f
Tx public key: ce2c67a4e861bb5e3fc28c990521bb191435fbadc05f3004d2c0a27791ae0acb
Timestamp: 1736749542 Timestamp [UCT]: 2025-01-13 06:25:42 Age [y:d:h:m:s]: 00:342:12:12:21
Block: 1196280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242335 RingCT/type: yes/0
Extra: 01ce2c67a4e861bb5e3fc28c990521bb191435fbadc05f3004d2c0a27791ae0acb02110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29065ff3a37c09498497a48b38f8775f9c4e9f4e87560d1c94369a30221efcd8 0.600000000000 1682877 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": 1196290, "vin": [ { "gen": { "height": 1196280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29065ff3a37c09498497a48b38f8775f9c4e9f4e87560d1c94369a30221efcd8" } } ], "extra": [ 1, 206, 44, 103, 164, 232, 97, 187, 94, 63, 194, 140, 153, 5, 33, 187, 25, 20, 53, 251, 173, 192, 95, 48, 4, 210, 192, 162, 119, 145, 174, 10, 203, 2, 17, 0, 0, 0, 10, 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