Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f576bd4cbcb0fc9ea42a74829b4ceebaf006c82db68663f6b5ef2743c61d5a6

Tx prefix hash: bdeb119b7d2fb9a0b5a3647643c83e8879cc9e46c8df81487d31aea419312a6b
Tx public key: 5c7837004b8b9f7852cd40beca6d72097448c73458505680d1428e00619c5bca
Timestamp: 1712634595 Timestamp [UCT]: 2024-04-09 03:49:55 Age [y:d:h:m:s]: 00:229:22:43:20
Block: 996470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164635 RingCT/type: yes/0
Extra: 015c7837004b8b9f7852cd40beca6d72097448c73458505680d1428e00619c5bca02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8636a7eeef5d8e8f2110b2495c98892275f294daa8b70f892cfc70ed99fb238a 0.600000000000 1456888 of 15

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": 996480, "vin": [ { "gen": { "height": 996470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8636a7eeef5d8e8f2110b2495c98892275f294daa8b70f892cfc70ed99fb238a" } } ], "extra": [ 1, 92, 120, 55, 0, 75, 139, 159, 120, 82, 205, 64, 190, 202, 109, 114, 9, 116, 72, 199, 52, 88, 80, 86, 128, 209, 66, 142, 0, 97, 156, 91, 202, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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