Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67209764ce66136c1151302896fc5b6552a015f5d74f97c8a6b455797bb5d235

Tx prefix hash: 5efc27b3398782921a01f4e6985207b152fc7a9e5b0f6a3c5a37b5cc47483f1b
Tx public key: 4e1e02d497078cdd76ee6cddbbdc39c3df4abf2907c8d8c76559eaa44410b12b
Timestamp: 1700796721 Timestamp [UCT]: 2023-11-24 03:32:01 Age [y:d:h:m:s]: 01:154:04:43:10
Block: 898344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371390 RingCT/type: yes/0
Extra: 014e1e02d497078cdd76ee6cddbbdc39c3df4abf2907c8d8c76559eaa44410b12b02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.647758907000 dcy

stealth address amount amount idx
00: 84caf5f3d78aa806bf152ff01d9f3c2f216fc7639a5ca5cce43a72fd4def7aed 0.647758907000 1354757 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": 898354, "vin": [ { "gen": { "height": 898344 } } ], "vout": [ { "amount": 647758907, "target": { "key": "84caf5f3d78aa806bf152ff01d9f3c2f216fc7639a5ca5cce43a72fd4def7aed" } } ], "extra": [ 1, 78, 30, 2, 212, 151, 7, 140, 221, 118, 238, 108, 221, 187, 220, 57, 195, 223, 74, 191, 41, 7, 200, 216, 199, 101, 89, 234, 164, 68, 16, 177, 43, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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