Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fb1046744a5810fe5392fee550d49b600722400d2bba487bed014b593cd601d

Tx prefix hash: b64da068930a4a92acd8b1f7b783d299a15347a211f492b340e3df17ac6c7a26
Tx public key: 2b2d3221572cd61c429f98a5ed526eb57c24e99ca05c2ad5f2e13a030470e960
Timestamp: 1628138118 Timestamp [UCT]: 2021-08-05 04:35:18 Age [y:d:h:m:s]: 03:147:11:48:26
Block: 307573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 878261 RingCT/type: yes/0
Extra: 012b2d3221572cd61c429f98a5ed526eb57c24e99ca05c2ad5f2e13a030470e96002110000000d01f1e57f000000000000000000

1 output(s) for total of 58.734191239000 dcy

stealth address amount amount idx
00: f964317b41e11a2c88081fb06f3b7557b38d8faa3169a6b9b38bf28367d98e84 58.734191239000 641148 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": 307583, "vin": [ { "gen": { "height": 307573 } } ], "vout": [ { "amount": 58734191239, "target": { "key": "f964317b41e11a2c88081fb06f3b7557b38d8faa3169a6b9b38bf28367d98e84" } } ], "extra": [ 1, 43, 45, 50, 33, 87, 44, 214, 28, 66, 159, 152, 165, 237, 82, 110, 181, 124, 36, 233, 156, 160, 92, 42, 213, 242, 225, 58, 3, 4, 112, 233, 96, 2, 17, 0, 0, 0, 13, 1, 241, 229, 127, 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