Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c735af3f907c0e7fbd92ce11b24eca841f89a8905e8712c0d0070c203e822e4c

Tx prefix hash: d9610902a05f25a8eec7984a6558aa754d77f5f3cd3fd820a19d247e23e6a5ae
Tx public key: 34b62611fa44dd15cbd67eee2953ad5b8a6ad756da9c5db5b8f46de3fcbbed53
Timestamp: 1736988115 Timestamp [UCT]: 2025-01-16 00:41:55 Age [y:d:h:m:s]: 00:333:14:34:21
Block: 1198237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235977 RingCT/type: yes/0
Extra: 0134b62611fa44dd15cbd67eee2953ad5b8a6ad756da9c5db5b8f46de3fcbbed53021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a3a6cad08d37bdd42b411bab759bc668d6e2fa33c3333f3282cdbe651cf3e19 0.600000000000 1684858 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": 1198247, "vin": [ { "gen": { "height": 1198237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a3a6cad08d37bdd42b411bab759bc668d6e2fa33c3333f3282cdbe651cf3e19" } } ], "extra": [ 1, 52, 182, 38, 17, 250, 68, 221, 21, 203, 214, 126, 238, 41, 83, 173, 91, 138, 106, 215, 86, 218, 156, 93, 181, 184, 244, 109, 227, 252, 187, 237, 83, 2, 17, 0, 0, 0, 7, 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