Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: babc0e2290ff99766f2b434aa22bf5f9f0c84ec7aef3934aefd4b204f30f5173

Tx prefix hash: 81c5d8ea7efee211758c2d76aa0801c6892e3f9fc57ede3447a12cd173a61e0b
Tx public key: 171ca0a767d9c5250c526ade84b828b3fcce17921dd4b6da8f6f92aa15a778a5
Timestamp: 1702150311 Timestamp [UCT]: 2023-12-09 19:31:51 Age [y:d:h:m:s]: 01:123:18:11:32
Block: 909578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349599 RingCT/type: yes/0
Extra: 01171ca0a767d9c5250c526ade84b828b3fcce17921dd4b6da8f6f92aa15a778a50211000000124b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3674fca738eac03405ef7d863f3de8af1df81914286b7c60b3515d95ee6922ac 0.600000000000 1366677 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": 909588, "vin": [ { "gen": { "height": 909578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3674fca738eac03405ef7d863f3de8af1df81914286b7c60b3515d95ee6922ac" } } ], "extra": [ 1, 23, 28, 160, 167, 103, 217, 197, 37, 12, 82, 106, 222, 132, 184, 40, 179, 252, 206, 23, 146, 29, 212, 182, 218, 143, 111, 146, 170, 21, 167, 120, 165, 2, 17, 0, 0, 0, 18, 75, 143, 81, 34, 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