Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77fff34c21cf4f8220247ae758b670a8f575af6fcca3991db275025a36c96f15

Tx prefix hash: cc36c6cc8b111feb0bc4bd7ff3e58a6e62c0db1fba2fd6b50055e41b57b10395
Tx public key: 36dc17fda5ec3371afe7ece91819832b1c6f5857da3d3db88a1ba884699f1cd4
Timestamp: 1703500667 Timestamp [UCT]: 2023-12-25 10:37:47 Age [y:d:h:m:s]: 01:105:17:50:34
Block: 920766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336689 RingCT/type: yes/0
Extra: 0136dc17fda5ec3371afe7ece91819832b1c6f5857da3d3db88a1ba884699f1cd4021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb6c281f2aaadd1719e437a512aef6a0eff313868e51cacdc12532e3429ebe2b 0.600000000000 1378450 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": 920776, "vin": [ { "gen": { "height": 920766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb6c281f2aaadd1719e437a512aef6a0eff313868e51cacdc12532e3429ebe2b" } } ], "extra": [ 1, 54, 220, 23, 253, 165, 236, 51, 113, 175, 231, 236, 233, 24, 25, 131, 43, 28, 111, 88, 87, 218, 61, 61, 184, 138, 27, 168, 132, 105, 159, 28, 212, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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