Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74f6cb0b1621902e8edc6e7ce2477f6e0e8f4f12ceb9fac0e819f8b741cfe424

Tx prefix hash: 4abb350c263a31564cd57d2bd4c613daa5580a6c2eb00432e923a6408db33c3f
Tx public key: bacf9a468e3cb51281090721226548cb47cb017975d40b413d42fabd906dd550
Timestamp: 1709129659 Timestamp [UCT]: 2024-02-28 14:14:19 Age [y:d:h:m:s]: 00:330:17:21:54
Block: 967438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236698 RingCT/type: yes/0
Extra: 01bacf9a468e3cb51281090721226548cb47cb017975d40b413d42fabd906dd5500211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5258bc0891d0443e462891ac6a22b87e153caecd811464d104bf500a64bfa5a 0.600000000000 1427217 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": 967448, "vin": [ { "gen": { "height": 967438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5258bc0891d0443e462891ac6a22b87e153caecd811464d104bf500a64bfa5a" } } ], "extra": [ 1, 186, 207, 154, 70, 142, 60, 181, 18, 129, 9, 7, 33, 34, 101, 72, 203, 71, 203, 1, 121, 117, 212, 11, 65, 61, 66, 250, 189, 144, 109, 213, 80, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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