Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 674b9bec577680a1e47a5cf9984303b3088ed562b5ad278917f86a1e8d92e7d0

Tx prefix hash: 8a01e9d55250b7efe5781c30ea2d7391faabcdaf8184fc8d80ad7ee83e801246
Tx public key: 7bde49918e9ac8c54bf3f0e418146577a66df3304477f86ad230d7b9ef2ba604
Timestamp: 1704731886 Timestamp [UCT]: 2024-01-08 16:38:06 Age [y:d:h:m:s]: 01:309:19:47:25
Block: 930963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480264 RingCT/type: yes/0
Extra: 017bde49918e9ac8c54bf3f0e418146577a66df3304477f86ad230d7b9ef2ba60402110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 053a7d3dce0a1962c8eba0f97ba3de8881676fb10385a5afc7296418e5ef7aa9 0.600000000000 1388855 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": 930973, "vin": [ { "gen": { "height": 930963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "053a7d3dce0a1962c8eba0f97ba3de8881676fb10385a5afc7296418e5ef7aa9" } } ], "extra": [ 1, 123, 222, 73, 145, 142, 154, 200, 197, 75, 243, 240, 228, 24, 20, 101, 119, 166, 109, 243, 48, 68, 119, 248, 106, 210, 48, 215, 185, 239, 43, 166, 4, 2, 17, 0, 0, 0, 5, 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