Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e90d70f74532a8b8d047936384c82e14dc22c42769718562f8f5b350a82c8c84

Tx prefix hash: aa8087210a38ce867eb5dc24bc592da3380a2fd24900420d6b8d55fb30d5ea2f
Tx public key: e168a4397a3b40cc5b0042295a3cc1ea34f6356c80e1577b5fe738be82b2f59b
Timestamp: 1722782147 Timestamp [UCT]: 2024-08-04 14:35:47 Age [y:d:h:m:s]: 00:289:15:46:55
Block: 1080616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206955 RingCT/type: yes/0
Extra: 01e168a4397a3b40cc5b0042295a3cc1ea34f6356c80e1577b5fe738be82b2f59b02110000001391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98e0a2551a86b103c4579320498cc2c65a1ca04c1a08acc6e93f9bb895922e1a 0.600000000000 1554049 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": 1080626, "vin": [ { "gen": { "height": 1080616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98e0a2551a86b103c4579320498cc2c65a1ca04c1a08acc6e93f9bb895922e1a" } } ], "extra": [ 1, 225, 104, 164, 57, 122, 59, 64, 204, 91, 0, 66, 41, 90, 60, 193, 234, 52, 246, 53, 108, 128, 225, 87, 123, 95, 231, 56, 190, 130, 178, 245, 155, 2, 17, 0, 0, 0, 19, 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