Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5566b32564db837d9af6a5b8f8b4d15e14e26ed6c7ca7c274149ee5fdd7af8c0

Tx prefix hash: 48dd0941cc079d8b2cf20a75a8106105cd26593c4ec36ad67f5af4a2b8ce3263
Tx public key: e5e7c8483172b0ad677eaa693a18cb20024f49ef69f001958a4d7cc6f56e680d
Timestamp: 1577666515 Timestamp [UCT]: 2019-12-30 00:41:55 Age [y:d:h:m:s]: 05:115:17:30:59
Block: 34658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1232509 RingCT/type: yes/0
Extra: 01e5e7c8483172b0ad677eaa693a18cb20024f49ef69f001958a4d7cc6f56e680d02110000000d4ac5aa02000000000000000000

1 output(s) for total of 471.155770189000 dcy

stealth address amount amount idx
00: 9ed8d3afc373aba9b2d039c3571d9b3b7b5da53ec7d92fed539b08578504f861 471.155770189000 58366 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": 34668, "vin": [ { "gen": { "height": 34658 } } ], "vout": [ { "amount": 471155770189, "target": { "key": "9ed8d3afc373aba9b2d039c3571d9b3b7b5da53ec7d92fed539b08578504f861" } } ], "extra": [ 1, 229, 231, 200, 72, 49, 114, 176, 173, 103, 126, 170, 105, 58, 24, 203, 32, 2, 79, 73, 239, 105, 240, 1, 149, 138, 77, 124, 198, 245, 110, 104, 13, 2, 17, 0, 0, 0, 13, 74, 197, 170, 2, 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