Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5533174579e459b4529a3de81e4574076a8e35297396decc69b466cc9bb134a8

Tx prefix hash: 1a4aaf3c9f1e43af8c977fa88c0eb4028e17f9249e7dbbb9856ad6d0f9481d24
Tx public key: 0b545b6e42df5f19cac92fe9dd8a0fb4a94adf88552ac02845b38fa792ea0e29
Timestamp: 1745000199 Timestamp [UCT]: 2025-04-18 18:16:39 Age [y:d:h:m:s]: 00:216:04:12:56
Block: 1264316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152216 RingCT/type: yes/0
Extra: 010b545b6e42df5f19cac92fe9dd8a0fb4a94adf88552ac02845b38fa792ea0e290211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d40c3e350ffa93f380c6fc6b36556d9c4a41453606bdbce8adadaf79763a875d 0.600000000000 1751513 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": 1264326, "vin": [ { "gen": { "height": 1264316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d40c3e350ffa93f380c6fc6b36556d9c4a41453606bdbce8adadaf79763a875d" } } ], "extra": [ 1, 11, 84, 91, 110, 66, 223, 95, 25, 202, 201, 47, 233, 221, 138, 15, 180, 169, 74, 223, 136, 85, 42, 192, 40, 69, 179, 143, 167, 146, 234, 14, 41, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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