Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b51f66c21385b23a26879878245d77dd7c58a4df303281a194ef780c783e6ae

Tx prefix hash: 004f40579003fa0519c548d6a148054af7bef88fba532fecd6bcb73cc82d1e18
Tx public key: b335efb4d5100e0e6324e448f79c70cbe9f4e9d1d5ecf67db126e7ed445c4d22
Timestamp: 1724273366 Timestamp [UCT]: 2024-08-21 20:49:26 Age [y:d:h:m:s]: 00:228:07:43:29
Block: 1092991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163029 RingCT/type: yes/0
Extra: 01b335efb4d5100e0e6324e448f79c70cbe9f4e9d1d5ecf67db126e7ed445c4d2202110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0082de45a0f5986089716bcbc5a610a28e314b22013c889125b9ce848977e348 0.600000000000 1567846 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": 1093001, "vin": [ { "gen": { "height": 1092991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0082de45a0f5986089716bcbc5a610a28e314b22013c889125b9ce848977e348" } } ], "extra": [ 1, 179, 53, 239, 180, 213, 16, 14, 14, 99, 36, 228, 72, 247, 156, 112, 203, 233, 244, 233, 209, 213, 236, 246, 125, 177, 38, 231, 237, 68, 92, 77, 34, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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