Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 091d4169647efbed09f9e0a279ed4fd796c9c4324db22383bf2737111ffbb89b

Tx prefix hash: 0dc91807b4c1050b18e7ca44cfac592dd592d719de472150a4d4245b9b6b80a3
Tx public key: cc174c68b679c3390f5b02658fc521d9ae237a1b1be7fabf829b837a9e1927fc
Timestamp: 1734541421 Timestamp [UCT]: 2024-12-18 17:03:41 Age [y:d:h:m:s]: 00:017:13:08:40
Block: 1178031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12526 RingCT/type: yes/0
Extra: 01cc174c68b679c3390f5b02658fc521d9ae237a1b1be7fabf829b837a9e1927fc0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1121f5a7d381246de0ff4b0a8e23be437ba6912be4912e5d28d5f0fb2e418530 0.600000000000 1664414 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": 1178041, "vin": [ { "gen": { "height": 1178031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1121f5a7d381246de0ff4b0a8e23be437ba6912be4912e5d28d5f0fb2e418530" } } ], "extra": [ 1, 204, 23, 76, 104, 182, 121, 195, 57, 15, 91, 2, 101, 143, 197, 33, 217, 174, 35, 122, 27, 27, 231, 250, 191, 130, 155, 131, 122, 158, 25, 39, 252, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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