Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9bb6b98db1bb06007f387d368ab3f9b41586e04a3c1cd886b4f9d59b44681c6

Tx prefix hash: 418e094e95378046bd9d8b9f40e48504e928eb6c3582a38e9692205394d0f67f
Tx public key: 78aa0fcdf47e5586c01ef433d00f9680b8d51b910a656edd8abe7287f73a7d4f
Timestamp: 1727478848 Timestamp [UCT]: 2024-09-27 23:14:08 Age [y:d:h:m:s]: 00:117:00:00:22
Block: 1119550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83618 RingCT/type: yes/0
Extra: 0178aa0fcdf47e5586c01ef433d00f9680b8d51b910a656edd8abe7287f73a7d4f021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32e03c2dc1a85a566c3627ac181d712eca8366cdcec15f4f50085a159184622b 0.600000000000 1601149 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": 1119560, "vin": [ { "gen": { "height": 1119550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32e03c2dc1a85a566c3627ac181d712eca8366cdcec15f4f50085a159184622b" } } ], "extra": [ 1, 120, 170, 15, 205, 244, 126, 85, 134, 192, 30, 244, 51, 208, 15, 150, 128, 184, 213, 27, 145, 10, 101, 110, 221, 138, 190, 114, 135, 247, 58, 125, 79, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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