Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 035e16bc2007a9590566bd105eb0b9ad1ee44a73c7aadc61b204d859d8be3700

Tx prefix hash: 35cd5ce9d48c767f7cd4bbfb9f95c290897b5e88f1ae194e37ae61e1942e2a3e
Tx public key: 58e9b27a353225402d7075190ad9c30bd302f77c9cc0c4f30a128dddcb86eef5
Timestamp: 1738011606 Timestamp [UCT]: 2025-01-27 21:00:06 Age [y:d:h:m:s]: 00:297:01:00:40
Block: 1206480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210038 RingCT/type: yes/0
Extra: 0158e9b27a353225402d7075190ad9c30bd302f77c9cc0c4f30a128dddcb86eef50211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b263d4a3e40fd149a8cc4ef6de7ab51d7d73b28a510251889c25ac56603730d6 0.600000000000 1693189 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": 1206490, "vin": [ { "gen": { "height": 1206480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b263d4a3e40fd149a8cc4ef6de7ab51d7d73b28a510251889c25ac56603730d6" } } ], "extra": [ 1, 88, 233, 178, 122, 53, 50, 37, 64, 45, 112, 117, 25, 10, 217, 195, 11, 211, 2, 247, 124, 156, 192, 196, 243, 10, 18, 141, 221, 203, 134, 238, 245, 2, 17, 0, 0, 0, 6, 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