Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 876d47458b9aa4c9e6567b100d08f2d67975179d8e8a22d29babe56ab29c8c6b

Tx prefix hash: a07733eac0f7372d13a7cc31b369160db73b4a0cd7aa6c6a87291bab7f901277
Tx public key: bc1a3b9d1b4bee19be681af1fda5883ac7d9e81a14d8273684d058ea6107afed
Timestamp: 1617471652 Timestamp [UCT]: 2021-04-03 17:40:52 Age [y:d:h:m:s]: 04:212:14:12:35
Block: 232554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1169974 RingCT/type: yes/0
Extra: 01bc1a3b9d1b4bee19be681af1fda5883ac7d9e81a14d8273684d058ea6107afed02110000000f9c1fbdcc000000000000000000

1 output(s) for total of 104.105207488000 dcy

stealth address amount amount idx
00: a3f443fa17f155be35a5181f116b6b17ff4299bd97663168c0e08087e060cced 104.105207488000 483154 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": 232564, "vin": [ { "gen": { "height": 232554 } } ], "vout": [ { "amount": 104105207488, "target": { "key": "a3f443fa17f155be35a5181f116b6b17ff4299bd97663168c0e08087e060cced" } } ], "extra": [ 1, 188, 26, 59, 157, 27, 75, 238, 25, 190, 104, 26, 241, 253, 165, 136, 58, 199, 217, 232, 26, 20, 216, 39, 54, 132, 208, 88, 234, 97, 7, 175, 237, 2, 17, 0, 0, 0, 15, 156, 31, 189, 204, 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