Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d45f12693e67f9eb70be64fad0ac164b956d3418da92571a6e862bd8efc10b0

Tx prefix hash: 564577ce30bc604843c0b614a1120640d7e2b606a5705b1315743656f1d49c8d
Tx public key: 8f9085531f2ff80cb46f8c04c0b8f248e0a272eff8642b7367cafbc75c48c5aa
Timestamp: 1621885223 Timestamp [UCT]: 2021-05-24 19:40:23 Age [y:d:h:m:s]: 03:351:11:53:55
Block: 266331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1013405 RingCT/type: yes/0
Extra: 018f9085531f2ff80cb46f8c04c0b8f248e0a272eff8642b7367cafbc75c48c5aa02110000001b85d8f8f2000000000000000000

1 output(s) for total of 80.453118044000 dcy

stealth address amount amount idx
00: 2bfb80d0d752416b2d7dd83e023e32aaa5e3298c3e6d2a9c5b10c45dd88fbcbc 80.453118044000 559639 of 0

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": 266341, "vin": [ { "gen": { "height": 266331 } } ], "vout": [ { "amount": 80453118044, "target": { "key": "2bfb80d0d752416b2d7dd83e023e32aaa5e3298c3e6d2a9c5b10c45dd88fbcbc" } } ], "extra": [ 1, 143, 144, 133, 83, 31, 47, 248, 12, 180, 111, 140, 4, 192, 184, 242, 72, 224, 162, 114, 239, 248, 100, 43, 115, 103, 202, 251, 199, 92, 72, 197, 170, 2, 17, 0, 0, 0, 27, 133, 216, 248, 242, 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