Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 566b92776f9b9af40e087dd835d80a90025c4f2514db1df3421af37d3f2b6301

Tx prefix hash: 0028aea5a2aeb185b7fbfc7902b4a0c121c82b660711eb39ff15bec9f191ae91
Tx public key: 90ba72420f16d7f1c6c6848d6c632fb9294ee17b2e847b4478592a56c8763c97
Timestamp: 1681532279 Timestamp [UCT]: 2023-04-15 04:17:59 Age [y:d:h:m:s]: 02:206:12:19:32
Block: 738879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 667446 RingCT/type: yes/0
Extra: 0190ba72420f16d7f1c6c6848d6c632fb9294ee17b2e847b4478592a56c8763c970211000000015029cbac000000000000000000

1 output(s) for total of 2.186690757000 dcy

stealth address amount amount idx
00: 186875bd3a3d45b2f2cb962c9285332e80d52898612dfd23c2726b2fbe955c85 2.186690757000 1185652 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": 738889, "vin": [ { "gen": { "height": 738879 } } ], "vout": [ { "amount": 2186690757, "target": { "key": "186875bd3a3d45b2f2cb962c9285332e80d52898612dfd23c2726b2fbe955c85" } } ], "extra": [ 1, 144, 186, 114, 66, 15, 22, 215, 241, 198, 198, 132, 141, 108, 99, 47, 185, 41, 78, 225, 123, 46, 132, 123, 68, 120, 89, 42, 86, 200, 118, 60, 151, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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