Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff0440bda9b7c1cce1c258b774db1673462e4f10d091ae064e938bfb1cfc513c

Tx prefix hash: 5abf4bbb482e0a7a8eff568b37db84b6f330e2c90c1595a9dfdbc5fa2c4c17d0
Tx public key: 836c76054f0efcb32367e82081f9bfaf53e9c42d1785cd3e410f5925bae94df0
Timestamp: 1666093078 Timestamp [UCT]: 2022-10-18 11:37:58 Age [y:d:h:m:s]: 03:047:15:33:55
Block: 611657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 814329 RingCT/type: yes/0
Extra: 01836c76054f0efcb32367e82081f9bfaf53e9c42d1785cd3e410f5925bae94df002110000000975e3f0e9000000000000000000

1 output(s) for total of 5.772002238000 dcy

stealth address amount amount idx
00: 2f9de1521cbc5b8093d18dc6b0d848f4f7e7c9d9457b8b6d57856db578b503fb 5.772002238000 1048773 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": 611667, "vin": [ { "gen": { "height": 611657 } } ], "vout": [ { "amount": 5772002238, "target": { "key": "2f9de1521cbc5b8093d18dc6b0d848f4f7e7c9d9457b8b6d57856db578b503fb" } } ], "extra": [ 1, 131, 108, 118, 5, 79, 14, 252, 179, 35, 103, 232, 32, 129, 249, 191, 175, 83, 233, 196, 45, 23, 133, 205, 62, 65, 15, 89, 37, 186, 233, 77, 240, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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