Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b50c2629ee9d5cb2bb4ea54f38fa09df505e864b9a9ae47683626445af47cbf

Tx prefix hash: ead84264d1f225f9271ba46c29938e1e0d844e1bd44c071b535dc48e5b45784f
Tx public key: a185f97893b1a84cd3fde804b474c3732e12b7439843c8b887952b2bb098905b
Timestamp: 1720205074 Timestamp [UCT]: 2024-07-05 18:44:34 Age [y:d:h:m:s]: 00:252:04:49:44
Block: 1059245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180207 RingCT/type: yes/0
Extra: 01a185f97893b1a84cd3fde804b474c3732e12b7439843c8b887952b2bb098905b0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 250db22cc17813cd6213a9800a50a7c4dd460b3831fd2e75d42c78ed37dc0307 0.600000000000 1529712 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": 1059255, "vin": [ { "gen": { "height": 1059245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "250db22cc17813cd6213a9800a50a7c4dd460b3831fd2e75d42c78ed37dc0307" } } ], "extra": [ 1, 161, 133, 249, 120, 147, 177, 168, 76, 211, 253, 232, 4, 180, 116, 195, 115, 46, 18, 183, 67, 152, 67, 200, 184, 135, 149, 43, 43, 176, 152, 144, 91, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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