Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cfa206ab218cc3e746c589642d1b2f4f5e84fcc1c6113868b878a18846525ab

Tx prefix hash: 61a87a1e4636a509ce3d296ac37586ccdc2dcae314b486876ea5301430ce56e0
Tx public key: 4f4b244c4dfedbb7ad6a29cd50946e352ed7731aeec41fc240f8028bf454364e
Timestamp: 1675484644 Timestamp [UCT]: 2023-02-04 04:24:04 Age [y:d:h:m:s]: 02:109:11:26:47
Block: 689387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 599890 RingCT/type: yes/0
Extra: 014f4b244c4dfedbb7ad6a29cd50946e352ed7731aeec41fc240f8028bf454364e02110000000483600029000000000000000000

1 output(s) for total of 3.189882013000 dcy

stealth address amount amount idx
00: 1e2dfee0e534506c80ceb23ec8fb1e4416c0218f302b14ca39dee0dc16b8bb36 3.189882013000 1132057 of 0

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": 689397, "vin": [ { "gen": { "height": 689387 } } ], "vout": [ { "amount": 3189882013, "target": { "key": "1e2dfee0e534506c80ceb23ec8fb1e4416c0218f302b14ca39dee0dc16b8bb36" } } ], "extra": [ 1, 79, 75, 36, 76, 77, 254, 219, 183, 173, 106, 41, 205, 80, 148, 110, 53, 46, 215, 115, 26, 238, 196, 31, 194, 64, 248, 2, 139, 244, 84, 54, 78, 2, 17, 0, 0, 0, 4, 131, 96, 0, 41, 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