Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10509c86464aefdde961013ce51afd57e78e06d749e2576e53c2349abc6cf12d

Tx prefix hash: ac7e47cee88fefeb427e1e0297d7e8073e51e2f72a2b50aaee80178633c8f385
Tx public key: 126aae31bbab0f8c6741b27e6533c3701214229604824891b5e4df8c2a5d3a9d
Timestamp: 1713471269 Timestamp [UCT]: 2024-04-18 20:14:29 Age [y:d:h:m:s]: 01:199:11:40:00
Block: 1003422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401228 RingCT/type: yes/0
Extra: 01126aae31bbab0f8c6741b27e6533c3701214229604824891b5e4df8c2a5d3a9d021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: caf8fa1fed9eaff7f739c3c5754ece62a7243efbbd7185c20b5f38080d9a0214 0.600000000000 1463956 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": 1003432, "vin": [ { "gen": { "height": 1003422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "caf8fa1fed9eaff7f739c3c5754ece62a7243efbbd7185c20b5f38080d9a0214" } } ], "extra": [ 1, 18, 106, 174, 49, 187, 171, 15, 140, 103, 65, 178, 126, 101, 51, 195, 112, 18, 20, 34, 150, 4, 130, 72, 145, 181, 228, 223, 140, 42, 93, 58, 157, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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