Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08666a66474ec377ce3bdfe958dd891cbdd9ae17382bb8299e6e478613c96552

Tx prefix hash: fdfcb98b308522aaa33b285cfb17a42bc84b9eefdfdba3f7feb28d7f65f8c583
Tx public key: 4593b4cff49fd5ac7aae5e3bbfd223c5067f2ccdaec71bc17cc32e61dd6e08ca
Timestamp: 1735538052 Timestamp [UCT]: 2024-12-30 05:54:12 Age [y:d:h:m:s]: 00:170:10:06:05
Block: 1186239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121522 RingCT/type: yes/0
Extra: 014593b4cff49fd5ac7aae5e3bbfd223c5067f2ccdaec71bc17cc32e61dd6e08ca021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 499cef6778f58cbdd79b0d93b9ae2d7cd307befc9581a685b1367689d2381011 0.600000000000 1672718 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": 1186249, "vin": [ { "gen": { "height": 1186239 } } ], "vout": [ { "amount": 600000000, "target": { "key": "499cef6778f58cbdd79b0d93b9ae2d7cd307befc9581a685b1367689d2381011" } } ], "extra": [ 1, 69, 147, 180, 207, 244, 159, 213, 172, 122, 174, 94, 59, 191, 210, 35, 197, 6, 127, 44, 205, 174, 199, 27, 193, 124, 195, 46, 97, 221, 110, 8, 202, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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