Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6200a70e72b763f0ebad9840194c0f49c703d15d9da79c2059c6a499690ace49

Tx prefix hash: 6f8a40ac7514e757329f6d442fe53b19f734c58c9498453be29e8f7bc95ae131
Tx public key: d310eba3c3f6fedc71e981c7c6344e772eb608ab77bcf2c6c5aa5dbeeb09763d
Timestamp: 1713926760 Timestamp [UCT]: 2024-04-24 02:46:00 Age [y:d:h:m:s]: 00:205:07:35:38
Block: 1007203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146980 RingCT/type: yes/0
Extra: 01d310eba3c3f6fedc71e981c7c6344e772eb608ab77bcf2c6c5aa5dbeeb09763d02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b89832d129f7491a6f9f1a24a33e43e0eff02cdfe1f0f6d04447908ac09dc1b9 0.600000000000 1468467 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": 1007213, "vin": [ { "gen": { "height": 1007203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b89832d129f7491a6f9f1a24a33e43e0eff02cdfe1f0f6d04447908ac09dc1b9" } } ], "extra": [ 1, 211, 16, 235, 163, 195, 246, 254, 220, 113, 233, 129, 199, 198, 52, 78, 119, 46, 182, 8, 171, 119, 188, 242, 198, 197, 170, 93, 190, 235, 9, 118, 61, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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