Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85220864672f7776d94c8073034be1aff4fc54a0c5c02d99a159bb87c19baca2

Tx prefix hash: 363789285b1cf9af4c6e3f0dc5ca305a8d4ac095e2e16287939a2ac8a59759f1
Tx public key: 89a61c899babeab39ea20ddb0fed30f243df696afa4f4f4b20aa24d91580aaa2
Timestamp: 1721546599 Timestamp [UCT]: 2024-07-21 07:23:19 Age [y:d:h:m:s]: 00:270:22:28:58
Block: 1070370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193570 RingCT/type: yes/0
Extra: 0189a61c899babeab39ea20ddb0fed30f243df696afa4f4f4b20aa24d91580aaa2021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a87c443ae22b53935b4e94b4c027dd483b3a190058bbd2c4ba3df0c2c09e9c9 0.600000000000 1542177 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": 1070380, "vin": [ { "gen": { "height": 1070370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a87c443ae22b53935b4e94b4c027dd483b3a190058bbd2c4ba3df0c2c09e9c9" } } ], "extra": [ 1, 137, 166, 28, 137, 155, 171, 234, 179, 158, 162, 13, 219, 15, 237, 48, 242, 67, 223, 105, 106, 250, 79, 79, 75, 32, 170, 36, 217, 21, 128, 170, 162, 2, 17, 0, 0, 0, 5, 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