Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9648160bf300b3b1428c17e46376ac84e2e31c06fbb31c604a5c1b6b4daf5e9

Tx prefix hash: a15e26cfa8cbb9d040b30de9bd4e2e9a04a29c0535a2a6bbaeb85f6147d08503
Tx public key: ce333d7ca0e86e8e80fcc113cfc454246518412f92ecb767be1a81baea3bc55d
Timestamp: 1712817615 Timestamp [UCT]: 2024-04-11 06:40:15 Age [y:d:h:m:s]: 00:318:03:23:29
Block: 997984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227444 RingCT/type: yes/0
Extra: 01ce333d7ca0e86e8e80fcc113cfc454246518412f92ecb767be1a81baea3bc55d0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc0ff52fdf27d8433fc1e04ebacdb69d889b503912c34e4b5d28d9647ab20d7d 0.600000000000 1458418 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": 997994, "vin": [ { "gen": { "height": 997984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc0ff52fdf27d8433fc1e04ebacdb69d889b503912c34e4b5d28d9647ab20d7d" } } ], "extra": [ 1, 206, 51, 61, 124, 160, 232, 110, 142, 128, 252, 193, 19, 207, 196, 84, 36, 101, 24, 65, 47, 146, 236, 183, 103, 190, 26, 129, 186, 234, 59, 197, 93, 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