Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fde86778c723327dbd7b00dfdd853a427c888b26b8ece50a23ca2bd418b5603e

Tx prefix hash: 059fee081d0fb6d3eba812c6ca219395328f5cd9f9069894fe96e4260aefbd08
Tx public key: 6fdd0f8ed7d136436280f9cd45a68d8a6299b13cebbe4fd750c175e0a8c369a0
Timestamp: 1698634885 Timestamp [UCT]: 2023-10-30 03:01:25 Age [y:d:h:m:s]: 01:171:07:09:47
Block: 880640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383433 RingCT/type: yes/0
Extra: 016fdd0f8ed7d136436280f9cd45a68d8a6299b13cebbe4fd750c175e0a8c369a0021100000003faf35c9c000000000000000000

1 output(s) for total of 0.741436771000 dcy

stealth address amount amount idx
00: b3990fcf9590a71b45aa4b841dcaeeea4527393e106cea0ff7e0512a3062884c 0.741436771000 1336204 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": 880650, "vin": [ { "gen": { "height": 880640 } } ], "vout": [ { "amount": 741436771, "target": { "key": "b3990fcf9590a71b45aa4b841dcaeeea4527393e106cea0ff7e0512a3062884c" } } ], "extra": [ 1, 111, 221, 15, 142, 215, 209, 54, 67, 98, 128, 249, 205, 69, 166, 141, 138, 98, 153, 177, 60, 235, 190, 79, 215, 80, 193, 117, 224, 168, 195, 105, 160, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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