Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5ef38de80ae37dafbd8fe973b497c8d7b613b410dcd85709f7115e997068a1b

Tx prefix hash: 641fc640624b1b83e1a7fdf74b650b14168de978873643e864efdbef144ba84f
Tx public key: fafabf8af1b4554934e83d0e5fb555f4984f770df9e3469db20befdccba0a7b8
Timestamp: 1731481163 Timestamp [UCT]: 2024-11-13 06:59:23 Age [y:d:h:m:s]: 01:032:16:05:55
Block: 1152637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281819 RingCT/type: yes/0
Extra: 01fafabf8af1b4554934e83d0e5fb555f4984f770df9e3469db20befdccba0a7b80211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cc00d3d86a6fa0e06bfaff7304d9e91fa0e18d0cb51bda1c64acc23cf63d32f 0.600000000000 1638240 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": 1152647, "vin": [ { "gen": { "height": 1152637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cc00d3d86a6fa0e06bfaff7304d9e91fa0e18d0cb51bda1c64acc23cf63d32f" } } ], "extra": [ 1, 250, 250, 191, 138, 241, 180, 85, 73, 52, 232, 61, 14, 95, 181, 85, 244, 152, 79, 119, 13, 249, 227, 70, 157, 178, 11, 239, 220, 203, 160, 167, 184, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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