Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b43a46bdd9de0941fc1d7d82544144baf4efbf218e9a215ab9e55cd00899e3b9

Tx prefix hash: b9246c6e43b645e0f039bb329729ea5e1189f066109d4dc2a9208326d7daf102
Tx public key: a4e508e0e32a83e352592493bd98c47091d3f249c5d4ee5f362334e8e25f02d0
Timestamp: 1711195310 Timestamp [UCT]: 2024-03-23 12:01:50 Age [y:d:h:m:s]: 01:315:00:17:10
Block: 984588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 483727 RingCT/type: yes/0
Extra: 01a4e508e0e32a83e352592493bd98c47091d3f249c5d4ee5f362334e8e25f02d002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0141182a2533e2898788487d3f0b1db20116dfb904270103f24d4b9da07b940 0.600000000000 1444759 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": 984598, "vin": [ { "gen": { "height": 984588 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0141182a2533e2898788487d3f0b1db20116dfb904270103f24d4b9da07b940" } } ], "extra": [ 1, 164, 229, 8, 224, 227, 42, 131, 227, 82, 89, 36, 147, 189, 152, 196, 112, 145, 211, 242, 73, 197, 212, 238, 95, 54, 35, 52, 232, 226, 95, 2, 208, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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