Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9a105c619904d63a922c1d0a6f311858b36388d6b8bdd4cdf46a29e51883da9

Tx prefix hash: 566a4f85458841d5545f8a476cf1dccf756ff14e437c6156101ed126fa9e83d6
Tx public key: 1c5987b2478425cb678e1ff616101d2fa61befaf6b4d514428efb67568fed8c6
Timestamp: 1700800684 Timestamp [UCT]: 2023-11-24 04:38:04 Age [y:d:h:m:s]: 01:348:00:28:38
Block: 898379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507605 RingCT/type: yes/0
Extra: 011c5987b2478425cb678e1ff616101d2fa61befaf6b4d514428efb67568fed8c60211000000014b8f5122000000000000000000

1 output(s) for total of 0.647585959000 dcy

stealth address amount amount idx
00: 0bfe7bbaf8154851db2f54be315b6a1c708e1482bbb075f1e60631c1690b2727 0.647585959000 1354792 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": 898389, "vin": [ { "gen": { "height": 898379 } } ], "vout": [ { "amount": 647585959, "target": { "key": "0bfe7bbaf8154851db2f54be315b6a1c708e1482bbb075f1e60631c1690b2727" } } ], "extra": [ 1, 28, 89, 135, 178, 71, 132, 37, 203, 103, 142, 31, 246, 22, 16, 29, 47, 166, 27, 239, 175, 107, 77, 81, 68, 40, 239, 182, 117, 104, 254, 216, 198, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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