Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a66259a33337da665b275d5cb85e1b0559644ac92596155cf3d88b94bb489757

Tx prefix hash: 1e08ce4507eae05111e34f37bb206eeda0af716a7c95f34a4b81e255772a62de
Tx public key: 1a9e3838c559dc27ea22ce377af91908e0d6e3b38dc3c37c348ca7dd8d86c60f
Timestamp: 1721949501 Timestamp [UCT]: 2024-07-25 23:18:21 Age [y:d:h:m:s]: 00:286:06:49:29
Block: 1073712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204542 RingCT/type: yes/0
Extra: 011a9e3838c559dc27ea22ce377af91908e0d6e3b38dc3c37c348ca7dd8d86c60f02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a091aa0888fca65c0f1cfe84793bb2e9763ad83cc415e2f4d7ccefd23cde5435 0.600000000000 1546219 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": 1073722, "vin": [ { "gen": { "height": 1073712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a091aa0888fca65c0f1cfe84793bb2e9763ad83cc415e2f4d7ccefd23cde5435" } } ], "extra": [ 1, 26, 158, 56, 56, 197, 89, 220, 39, 234, 34, 206, 55, 122, 249, 25, 8, 224, 214, 227, 179, 141, 195, 195, 124, 52, 140, 167, 221, 141, 134, 198, 15, 2, 17, 0, 0, 0, 5, 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