Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cbfb5be56eb7fa2e9bff47587b06e1ed30700cb43ddc980fe26800b43bf5133

Tx prefix hash: e457e39094b05e60347b9b4ad6d7e9087bccc3fc722e8af5f962f127f62237e5
Tx public key: 7eb0f511fa1ea3d577a41d20a3828e701765f1c571ccaaed3aba87a8f0ec3112
Timestamp: 1720826096 Timestamp [UCT]: 2024-07-12 23:14:56 Age [y:d:h:m:s]: 00:337:19:36:46
Block: 1064418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241304 RingCT/type: yes/0
Extra: 017eb0f511fa1ea3d577a41d20a3828e701765f1c571ccaaed3aba87a8f0ec3112021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e71c9570f484d03394d75bdf4e9acc728c804a7d069aa38dccb5c1f91fd19556 0.600000000000 1534943 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": 1064428, "vin": [ { "gen": { "height": 1064418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e71c9570f484d03394d75bdf4e9acc728c804a7d069aa38dccb5c1f91fd19556" } } ], "extra": [ 1, 126, 176, 245, 17, 250, 30, 163, 213, 119, 164, 29, 32, 163, 130, 142, 112, 23, 101, 241, 197, 113, 204, 170, 237, 58, 186, 135, 168, 240, 236, 49, 18, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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