Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54ce7468347aac6eabfa6c3f0cb7de5dde7af1ea8b77fe816adb4145656c8352

Tx prefix hash: 90fbcfe656294607f464c41030c810f12e998731b7a90943c0b3155d9237b6ba
Tx public key: 3d2cdd08a88da169d8a6f000e27dfcd7ed1ea279c3b13335434181b77a4eba92
Timestamp: 1735120179 Timestamp [UCT]: 2024-12-25 09:49:39 Age [y:d:h:m:s]: 00:094:22:22:24
Block: 1182792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67623 RingCT/type: yes/0
Extra: 013d2cdd08a88da169d8a6f000e27dfcd7ed1ea279c3b13335434181b77a4eba920211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 077fa50756a9b7d49735301972df86fab02da0ea1219a524a923623080e86e46 0.600000000000 1669231 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": 1182802, "vin": [ { "gen": { "height": 1182792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "077fa50756a9b7d49735301972df86fab02da0ea1219a524a923623080e86e46" } } ], "extra": [ 1, 61, 44, 221, 8, 168, 141, 161, 105, 216, 166, 240, 0, 226, 125, 252, 215, 237, 30, 162, 121, 195, 177, 51, 53, 67, 65, 129, 183, 122, 78, 186, 146, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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