Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16e85a605ccd1f7978119cc8be5c6663ac82b68cee111f649cab75f7aefdf433

Tx prefix hash: 6eaa78197e606213f5c189019e253a30f2d793d8f507ea671877d2e63ae5bbee
Tx public key: 2f2df35cf893ca8e3c2bc492edf4beb33d1d64407156ea6ef6705e7dd3480da0
Timestamp: 1728479057 Timestamp [UCT]: 2024-10-09 13:04:17 Age [y:d:h:m:s]: 00:028:23:39:39
Block: 1127851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20680 RingCT/type: yes/0
Extra: 012f2df35cf893ca8e3c2bc492edf4beb33d1d64407156ea6ef6705e7dd3480da002110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93371d879566b246cf5bdcb7ff23907774d9f87b9aa4ec761819f71d9e9b7433 0.600000000000 1610664 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": 1127861, "vin": [ { "gen": { "height": 1127851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93371d879566b246cf5bdcb7ff23907774d9f87b9aa4ec761819f71d9e9b7433" } } ], "extra": [ 1, 47, 45, 243, 92, 248, 147, 202, 142, 60, 43, 196, 146, 237, 244, 190, 179, 61, 29, 100, 64, 113, 86, 234, 110, 246, 112, 94, 125, 211, 72, 13, 160, 2, 17, 0, 0, 0, 10, 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