Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66635b096f73fbc0ea8ed3a65c95840b0e9150b8af63dd0ed4159ce866283dd4

Tx prefix hash: 0df8b7d43671c69ce169e0d935a79601c403d76c85456d52d809e7a48916ff44
Tx public key: 2a49d73d0a71d6b1056782cc3bc55cf04d1cc425f40320bab62abd4ccdcb789e
Timestamp: 1723484373 Timestamp [UCT]: 2024-08-12 17:39:33 Age [y:d:h:m:s]: 00:248:13:06:05
Block: 1086442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177522 RingCT/type: yes/0
Extra: 012a49d73d0a71d6b1056782cc3bc55cf04d1cc425f40320bab62abd4ccdcb789e02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47ef7d2a85a51cfc2552cd1ef8bc8e4c006a6ae6c7cec5eddfb97a365cd9859e 0.600000000000 1561039 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": 1086452, "vin": [ { "gen": { "height": 1086442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47ef7d2a85a51cfc2552cd1ef8bc8e4c006a6ae6c7cec5eddfb97a365cd9859e" } } ], "extra": [ 1, 42, 73, 215, 61, 10, 113, 214, 177, 5, 103, 130, 204, 59, 197, 92, 240, 77, 28, 196, 37, 244, 3, 32, 186, 182, 42, 189, 76, 205, 203, 120, 158, 2, 17, 0, 0, 0, 10, 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