Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2d797a8698b5077604575a2a6856de90e175d9ab7845d2e14783521d14b222c

Tx prefix hash: 71369778c8e8d4f4d387ed720861a6cc60bcc8c2692ef614238dcb1bf8f7671a
Tx public key: e0d7e24193e4da2bbae566d0a5b7a1e15ffdc66e3d6408cc77ed4105b5aa2cd0
Timestamp: 1714320283 Timestamp [UCT]: 2024-04-28 16:04:43 Age [y:d:h:m:s]: 00:334:03:26:41
Block: 1010456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238871 RingCT/type: yes/0
Extra: 01e0d7e24193e4da2bbae566d0a5b7a1e15ffdc66e3d6408cc77ed4105b5aa2cd002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bff27183828c2fd03863bde3c2e05e208f9d7aeb6c8ea41c65b4de01f19da4a 0.600000000000 1472422 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": 1010466, "vin": [ { "gen": { "height": 1010456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bff27183828c2fd03863bde3c2e05e208f9d7aeb6c8ea41c65b4de01f19da4a" } } ], "extra": [ 1, 224, 215, 226, 65, 147, 228, 218, 43, 186, 229, 102, 208, 165, 183, 161, 225, 95, 253, 198, 110, 61, 100, 8, 204, 119, 237, 65, 5, 181, 170, 44, 208, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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