Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9dda76c8e6468622daf1a13558ee03aba9a0dc66d3689c196bc151762b3db9f

Tx prefix hash: 811b68089489d477f24ff44ab6a18b971700ad79fc36a021e83f437dcb17fae7
Tx public key: 89841da3ba6b46c6bc9cbafcffd8b6dc5b5a3fb1cffa709a1fc12d64536512d7
Timestamp: 1740647477 Timestamp [UCT]: 2025-02-27 09:11:17 Age [y:d:h:m:s]: 00:267:14:19:47
Block: 1228269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189011 RingCT/type: yes/0
Extra: 0189841da3ba6b46c6bc9cbafcffd8b6dc5b5a3fb1cffa709a1fc12d64536512d70211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 464d2191df8cab472dadf07c0666e3bf918c996209ff57fe8b19e55e37d2d515 0.600000000000 1715146 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": 1228279, "vin": [ { "gen": { "height": 1228269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "464d2191df8cab472dadf07c0666e3bf918c996209ff57fe8b19e55e37d2d515" } } ], "extra": [ 1, 137, 132, 29, 163, 186, 107, 70, 198, 188, 156, 186, 252, 255, 216, 182, 220, 91, 90, 63, 177, 207, 250, 112, 154, 31, 193, 45, 100, 83, 101, 18, 215, 2, 17, 0, 0, 0, 3, 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