Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d00dae03cbdc5912f476439923399cd9ccf7e628d3564d280482d30d124a423

Tx prefix hash: 0b310f8b182c7297ab43e4664a571c7adbb205ebae9ba3da6aa7b376663becd7
Tx public key: 66e62bd2c6e756407893cc71a17c2dc431b2c68633a69fef29d886309ad88dd6
Timestamp: 1700892887 Timestamp [UCT]: 2023-11-25 06:14:47 Age [y:d:h:m:s]: 02:040:08:28:09
Block: 899146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 548670 RingCT/type: yes/0
Extra: 0166e62bd2c6e756407893cc71a17c2dc431b2c68633a69fef29d886309ad88dd6021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.643807503000 dcy

stealth address amount amount idx
00: 4b7d1a777c14a7ac36649e4398b3c781a652537af0436d1693a05f4eeebcd0f5 0.643807503000 1355589 of 0

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": 899156, "vin": [ { "gen": { "height": 899146 } } ], "vout": [ { "amount": 643807503, "target": { "key": "4b7d1a777c14a7ac36649e4398b3c781a652537af0436d1693a05f4eeebcd0f5" } } ], "extra": [ 1, 102, 230, 43, 210, 198, 231, 86, 64, 120, 147, 204, 113, 161, 124, 45, 196, 49, 178, 198, 134, 51, 166, 159, 239, 41, 216, 134, 48, 154, 216, 141, 214, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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