Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89b6561857dc81fbac9df78ad1b912eee4a728c5fea79f7c6f40516e35b4d8df

Tx prefix hash: 33dfd52ec441234331304ea1fab67da4052f5eeb71549b68488f2009ad8470fe
Tx public key: 2000ba7deab3b2017c4ab88c1002afc45b7e3c8b1420b1d2062dd0ef056d3347
Timestamp: 1588732547 Timestamp [UCT]: 2020-05-06 02:35:47 Age [y:d:h:m:s]: 05:183:01:17:10
Block: 98554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1305975 RingCT/type: yes/0
Extra: 012000ba7deab3b2017c4ab88c1002afc45b7e3c8b1420b1d2062dd0ef056d334702110000000260e3cc90000000000000000000

1 output(s) for total of 289.367965146000 dcy

stealth address amount amount idx
00: 517f918aeacc40d12e9f76eb102febcc843dd9ab0fb2fbaee8a28bb785611506 289.367965146000 174224 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": 98564, "vin": [ { "gen": { "height": 98554 } } ], "vout": [ { "amount": 289367965146, "target": { "key": "517f918aeacc40d12e9f76eb102febcc843dd9ab0fb2fbaee8a28bb785611506" } } ], "extra": [ 1, 32, 0, 186, 125, 234, 179, 178, 1, 124, 74, 184, 140, 16, 2, 175, 196, 91, 126, 60, 139, 20, 32, 177, 210, 6, 45, 208, 239, 5, 109, 51, 71, 2, 17, 0, 0, 0, 2, 96, 227, 204, 144, 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