Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b2ee4d16f9d4f6bc85773be95783701f53a840bfa612ccd4c2b32dbf1e6c6e0

Tx prefix hash: 877aa1f51d92381b089a47a3382a47beb80f00f1ad3efb8c9a31877fe232880c
Tx public key: d0f6e0d36e4b6fe9767ca36217ac1646e5a913e3efb6d81c54a3ddf44e043694
Timestamp: 1718024475 Timestamp [UCT]: 2024-06-10 13:01:15 Age [y:d:h:m:s]: 00:279:22:28:19
Block: 1041176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200071 RingCT/type: yes/0
Extra: 01d0f6e0d36e4b6fe9767ca36217ac1646e5a913e3efb6d81c54a3ddf44e0436940211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72d4a06b3919bdd80ee43e1c815c77dfcf337bb52bf51a18c477163b2c9a55af 0.600000000000 1509841 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": 1041186, "vin": [ { "gen": { "height": 1041176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72d4a06b3919bdd80ee43e1c815c77dfcf337bb52bf51a18c477163b2c9a55af" } } ], "extra": [ 1, 208, 246, 224, 211, 110, 75, 111, 233, 118, 124, 163, 98, 23, 172, 22, 70, 229, 169, 19, 227, 239, 182, 216, 28, 84, 163, 221, 244, 78, 4, 54, 148, 2, 17, 0, 0, 0, 4, 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