Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5aabad0fb6289a0be071d16e0380bcf3fb5b727f48fe5e50461ed8743b09fd17

Tx prefix hash: 8162313c2fadc9f8ab55c9d2b8494074b699b5483c1659b5bdc78d25f123ffa9
Tx public key: 3fa393c5afac4de91cc26babd131094a6a52ee1a708a887d8d2e3070182a1e56
Timestamp: 1722196743 Timestamp [UCT]: 2024-07-28 19:59:03 Age [y:d:h:m:s]: 00:252:08:48:59
Block: 1075763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180265 RingCT/type: yes/0
Extra: 013fa393c5afac4de91cc26babd131094a6a52ee1a708a887d8d2e3070182a1e5602110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b81bba0d5168c99bc155447af77645935e32a941d710d06fb088ee0d5fd994c9 0.600000000000 1548292 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": 1075773, "vin": [ { "gen": { "height": 1075763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b81bba0d5168c99bc155447af77645935e32a941d710d06fb088ee0d5fd994c9" } } ], "extra": [ 1, 63, 163, 147, 197, 175, 172, 77, 233, 28, 194, 107, 171, 209, 49, 9, 74, 106, 82, 238, 26, 112, 138, 136, 125, 141, 46, 48, 112, 24, 42, 30, 86, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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